Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] MONGO_OPTIONS being ignored for oplog connection #23314

Conversation

cuonghuunguyen
Copy link
Contributor

Proposed changes (including videos or screenshots)

Issue(s)

Fixes #23313

Steps to test or reproduce

Further comments

@cuonghuunguyen cuonghuunguyen force-pushed the meomay503/oplog-replicaset-is-required-19064 branch 3 times, most recently from e126121 to c857e91 Compare September 30, 2021 04:06
@cuonghuunguyen cuonghuunguyen force-pushed the meomay503/oplog-replicaset-is-required-19064 branch from c857e91 to b5f7600 Compare September 30, 2021 04:45
@debdutdeb debdutdeb requested review from casalsgh and a team October 1, 2021 06:17
@casalsgh casalsgh requested a review from sampaiodiego October 20, 2021 14:42
sampaiodiego
sampaiodiego previously approved these changes Oct 20, 2021
@sampaiodiego sampaiodiego changed the title [FIX] Fix cannot connect custom OPLOG to MongoDB via SSL [FIX] MONGO_OPTIONS being ignored for oplog connection Oct 20, 2021
@sampaiodiego sampaiodiego merged commit 514ccd9 into RocketChat:develop Oct 20, 2021
@sampaiodiego sampaiodiego mentioned this pull request Oct 28, 2021
@cuonghuunguyen cuonghuunguyen deleted the meomay503/oplog-replicaset-is-required-19064 branch December 13, 2021 04:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BREAKING BUG] Cannot use Custom OPLOG with MongoDB which require SSL connection
2 participants